Method, apparatus, and computer-readable medium for transmission of files over a web socket connection in a networked collaboration workspace

ABSTRACT

A system, method and computer-readable medium for transmission of files over a web socket connection in a networked collaboration workspace, including transmitting a representation of a collaboration workspace hosted on a server and accessible to participants over a web socket connection, the representation of the collaboration workspace comprising remote participant objects corresponding to remote computing devices connected to the server, generating one or more live folders corresponding to the remote participant objects, each live folder being mapped to a network address of a remote computing device corresponding to the remote participant object, detecting a user input to drag an icon corresponding to a file proximate to a remote participant object, and storing the at least one file in a live folder corresponding to the remote participant object to thereby transmit the at least one file to the network address of the remote computing device over the web socket connection.

BACKGROUND

This application is a continuation-in-part of U.S. application Ser. No. 15/685,533, titled “METHOD, APPARATUS, AND COMPUTER-READABLE MEDIUM FOR IMPLEMENTATION OF A UNIVERSAL HARDWARE-SOFTWARE INTERFACE” and filed Aug. 24, 2017, the disclosure of which is hereby incorporated by reference in its entirety.

BACKGROUND

Operating systems and applications executing within operating systems frequently make use of external hardware devices to allow users to provide input to the program and to provide output to users. Common examples of external hardware devices include a keyboard, a computer mouse, a microphone, and external speakers. These external hardware devices interface with the operating system through the use of drivers, which are specialized software programs configured to interface between the hardware commands used by a particular hardware device and the operating system.

Applications will sometimes be designed to interface with certain hardware devices. For example, a voice-to-text word processing application can be designed to interface with an audio headset including a microphone. In this case, the application must be specifically configured to receive voice commands, perform voice recognition, convert the recognized words into textual content, and output the textual content into a document. This functionality will typically be embodied in the application's Application Programming Interface (API), which is a set of defined methods of communication between various software components. In the example of the voice recognition application, the API can include an interface between the application program and software on a driver that is responsible for interfacing with the hardware device (the microphone) itself.

One problem with existing software that makes use of specialized hardware devices is that the application or operating system software itself must be customized and specially designed in order to utilize the hardware device. This customization means that the hardware device cannot exceed the scope defined for it by the application and cannot be utilized for contexts outside the specific application for which it was designed to be used. For example, a user of the voice-to-text word processing application could not manipulate other application programs or other components within the operating system using voice commands unless those other application programs or the operating system were specifically designed to make use of voice commands received over the microphone.

FIG. 1 illustrates an example of the existing architecture of systems which make use of coupled hardware devices for user input. The operating system 100A of FIG. 1 includes executing applications 101A and 102A, each of which have their own APIs, 101B and 102B, respectively. The operating system 100A also has its own API 100B, as well as specialized drivers 100C, 101C, and 102C, configured to interface with hardware devices 100D, 101D, and 102D.

As shown in FIG. 1, application API 101B is configured to interface with driver 101C which itself interfaces with hardware device 101D. Similarly, application API 102B is configured to interface with driver 102C which itself interfaces with hardware device 102D. At the operating system level, the operating system API 100B is configured to interface with driver 100C, which itself interfaces with hardware device 100D.

The architecture of the system shown in FIG. 1 limits the ability of users to utilize hardware devices outside of certain application or operating system contexts. For example, a user could not utilize hardware device 101D to provide input to application 102A and could not utilize hardware device 102D to provide input to application 101A or to the operating system 100A.

Accordingly, improvements are needed in hardware-software interfaces which allow for utilization of hardware devices in multiple software contexts.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of the existing architecture of systems which make use of coupled hardware devices for user input.

FIG. 2 illustrates the architecture of a system utilizing the universal hardware-software interface according to an exemplary embodiment.

FIG. 3 illustrates a flowchart for implementation of a universal hardware-software interface according to an exemplary embodiment.

FIG. 4 illustrates a flowchart for determining a user input based at least in part on information captured by one or more hardware devices communicatively coupled to the system when the information captured by the one or more hardware devices comprises one or more images according to an exemplary embodiment.

FIG. 5A illustrates an example of object recognition according to an exemplary embodiment.

FIG. 5B illustrates an example of determining input location coordinates according to an exemplary embodiment.

FIG. 6 illustrates a flowchart for determining a user input based at least in part on information captured by one or more hardware devices communicatively coupled to the system when the captured information is sound information according to an exemplary embodiment.

FIG. 7 illustrates a tool interface that can be part of the transparent layer according to an exemplary embodiment.

FIG. 8 illustrates an example of a stylus that can be part of the system according to an exemplary embodiment.

FIG. 9 illustrates a flowchart for identifying a context corresponding to the user input according to an exemplary embodiment.

FIG. 10 illustrates an example of using the input coordinates to determine a context according to an exemplary embodiment.

FIG. 11 illustrates a flowchart for converting user input into transparent layer commands according to an exemplary embodiment.

FIG. 12A illustrates an example of receiving input coordinates when the selection mode is toggled according to an exemplary embodiment.

FIG. 12B illustrates an example of receiving input coordinates when the pointing mode is toggled according to an exemplary embodiment.

FIG. 12C illustrates an example of receiving input coordinates when the drawing mode is toggled according to an exemplary embodiment.

FIG. 13 illustrates an example of a transparent layer command determined based on one or more words identified in input voice data according to an exemplary embodiment.

FIG. 14 illustrates another example of a transparent layer command determined based on one or more words identified in input voice data according to an exemplary embodiment.

FIG. 15 illustrates a flowchart for executing the one or more transparent layer commands on the transparent layer according to an exemplary embodiment.

FIG. 16 illustrates an example interface for adding new commands corresponding to user input according to an exemplary embodiment.

FIG. 17 illustrates various components and options of a drawing interface and draw mode according to an exemplary embodiment.

FIG. 18 illustrates a calibration and settings interface for a video camera hardware device that is used to recognize objects and allows for a user to provide input using touch and gestures according to an exemplary embodiment.

FIG. 19 illustrates a general settings interface that allows a user to customize various aspects of the interface, toggle input modes, and make other changes according to an exemplary embodiment.

FIG. 20 illustrates a flowchart for transmission of files over a web socket connection in a networked collaboration workspace according to an exemplary embodiment.

FIG. 21A illustrates the network architecture used to host and transmit collaboration workspace according to an exemplary embodiment.

FIG. 21B illustrates the process for propagating edits to the collaboration workspace within the network according to an exemplary embodiment.

FIG. 22 illustrates multiple representations of a collaboration workspace according to an exemplary embodiment.

FIG. 23 illustrates a flowchart for generating one or more live folders corresponding to the one or more remote participant objects according to an exemplary embodiment.

FIG. 24 illustrates an example of a querying process according to an exemplary embodiment.

FIG. 25 illustrates an example of generating one or more local folders corresponding to the one or more remote participants according to an exemplary embodiment.

FIG. 26 illustrates an example of mapping the one or more local folders to the one or more IP addresses according to an exemplary embodiment.

FIG. 27 illustrates an example of the drag and drop process and detection according to an exemplary embodiment.

FIG. 28 illustrates another example of the drag and drop process and detection according to an exemplary embodiment.

FIG. 29 illustrates a flowchart for storing the at least one file in a live folder corresponding to the remote participant object and to transmit the at least one file to the network address of the remote computing device over the web socket connection according to an exemplary embodiment.

FIG. 30 illustrates an exemplary computing environment configured to carry out the disclosed methods.

DETAILED DESCRIPTION

While methods, apparatuses, and computer-readable media are described herein by way of examples and embodiments, those skilled in the art recognize that methods, apparatuses, and computer-readable media for implementation of a universal hardware-software interface are not limited to the embodiments or drawings described. It should be understood that the drawings and description are not intended to be limited to the particular form disclosed. Rather, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the appended claims. Any headings used herein are for organizational purposes only and are not meant to limit the scope of the description or the claims. As used herein, the word “can” is used in a permissive sense (i.e., meaning having the potential to) rather than the mandatory sense (i.e., meaning must). Similarly, the words “include,” “including,” and “includes” mean including, but not limited to.

Applicant has discovered a method, apparatus, and computer-readable medium that solves the problems associated with previous hardware-software interfaces used for hardware devices. In particular, Applicant has developed a universal hardware-software interface which allows users to utilize communicatively-coupled hardware devices in a variety of software contexts. The disclosed implementation removes the need for applications or operating systems to be custom designed to interface with a particular hardware device through the use of a specialized virtual driver and a corresponding transparent layer, as is described below in greater detail.

FIG. 2 illustrates the architecture of a system utilizing the universal hardware-software interface according to an exemplary embodiment. As shown in FIG. 2, the operating system 200A includes a transparent layer 203 which communicates a virtual driver 204. As will be explained in greater detail below, the transparent layer 203 is an API configured to interface between a virtual driver and an operating system and/or application(s) executing on the operating system. In this example, the transparent layer 203 interfaces between the virtual driver 204 and API 201B of application 201A, API 202B of application 202A, and operating system API 200B of operating system 200A.

The transparent layer 203 can be part of a software process running on the operating system and can have its own user interface (UI) elements, including a transparent UI superimposed on an underlying user interface and/or visible UI elements that a user is able to interact with.

The virtual driver 204 is configured to emulate drivers 205A and 205B, which interface with hardware devices 206A and 206B, respectively. The virtual driver can receive user input that instructs the virtual driver on which virtual driver to emulate, for example, in the form of a voice command, a selection made on a user interface, and/or a gesture made by the user in front of a coupled web camera. For example, each of the connected hardware devices can operate in a “listening” mode and each of the emulated drivers in the virtual driver 204 can be configured to detect an initialization signal which serves as a signal to the virtual driver to switch to a particular emulation mode. For example, a user stating “start voice commands” can activate the driver corresponding to a microphone to receive a new voice command. Similarly, a user giving a certain gesture can activate the driver corresponding to a web camera to receive gesture input or touch input.

The virtual driver can also be configured to interface with a native driver, such as native driver 205C, which itself communicates with hardware device 206C. In one example, hardware device 206C can be a standard input device, such as a keyboard or a mouse, which is natively supported by the operating system.

The system shown in FIG. 2 allows for implementation of a universal hardware-software interface in which users can utilize any coupled hardware device in a variety of contexts, such as a particular application or the operating system, without requiring the application or operating system to be customized to interface with the hardware device.

For example, hardware device 206A can capture information which is then received by the virtual driver 204 emulating driver 205A. The virtual driver 204 can determine a user input based upon the captured information. For example, if the information is a series of images of a user moving their hand, the virtual driver can determine that the user has performed a gesture.

Based upon an identified context (such as a particular application or the operating system), the user input can be converted into a transparent layer command and transmitted to the transparent layer 203 for execution. The transparent layer command can include native commands in the identified context. For example, if the identified context is application 201A, then the native commands would be in a format that is compatible with application API 201B of application 201A. Execution of the transparent layer command can then be configured to cause execution of one or more native commands in the identified context. This is accomplished by the transparent layer 203 interfacing with each of the APIs of the applications executing on the operating system 200A as well as the operating system API 200B. For example, if the native command is an operating system command, such as a command to launch a new program, then the transparent layer 203 can provide that native command to the operating system API 200B for execution.

As shown in FIG. 2, there is bidirectional communication between all of the components shown. This means, for example, that execution of a transparent layer command in the transparent layer 203 can result in transmission of information to the virtual driver 204 and on to one of the connected hardware devices. For example, after a voice command is recognized as input, converted to a transparent layer command including a native command, and executed by the transparent layer (resulting in execution of the native command in the identified context), a signal can be sent from the transparent layer to a speaker (via the virtual driver) to transmit the sound output “command received.”

Of course, the architecture shown in FIG. 2 is for the purpose of explanation only, and it is understood that the number of applications executing, number and type of connected hardware devices, number of drivers, and emulated drivers can vary.

FIG. 3 illustrates a flowchart for implementation of a universal hardware-software interface according to an exemplary embodiment.

At step 301 a user input is determined based at least in part on information captured by one or more hardware devices communicatively coupled to the system. The system, as used herein, can refer to one or more computing devices executing the steps of the method, an apparatus comprising one or more processors and one or more memories executing the steps of the method, or any other computing system.

The user input can be determined by a virtual driver executing on the system. As discussed earlier, virtual driver can be operating in an emulation mode in which it is emulating other hardware drivers and thereby receiving the captured information from a hardware device or can optionally receive the captured information from one or more other hardware drivers which are configured to interface with a particular hardware device.

A variety of hardware devices can be utilized, such as a camera, a video camera, a microphone, a headset having bidirectional communication, a mouse, a touchpad, a trackpad, a controller, a game pad, a joystick, a touch screen, a motion capture device including accelerometers and/or a tilt sensors, a remote, a stylus, or any combination of these devices. Of course, this list of hardware devices is provided by way of example only, and any hardware device which can be utilized to detect voice, image, video, or touch information can be utilized.

The communicative coupling between the hardware devices and the system can take a variety of forms. For example, the hardware device can communicate with the system via a wireless network, Bluetooth protocol, radio frequency, infrared signals, and/or by a physical connection such as a Universal Serial Bus (USB) connection. The communication can also include both wireless and wired communications. For example, a hardware device can include two components, one of which wirelessly (such as over Bluetooth) transmits signals to a second component which itself connects to the system via a wired connection (such as USB). A variety of communication techniques can be utilized in accordance with the system described herein, and these examples are not intended to be limiting.

The information captured by the one or more hardware devices can be any type of information, such as image information including one or more images, frames of a video, sound information, and/or touch information. The captured information can be in any suitable format, such as .wav or .mp3 files for sound information, .jpeg files for images, numerical coordinates for touch information, etc.

The techniques described herein can allow for any display device to function effectively as a “touch” screen device in any context, even if the display device does not include any hardware to detect touch signals or touch-based gestures. This is described in greater detail below and can be accomplished through analysis of images captured by a camera or a video camera.

FIG. 4 illustrates a flowchart for determining a user input based at least in part on information captured by one or more hardware devices communicatively coupled to the system when the information captured by the one or more hardware devices comprises one or more images.

At step 401 one or more images are received. These images can be captured by a hardware device such as a camera or video camera and can be received by the virtual driver, as discussed earlier.

At step 402 an object in the one or more images is recognized. The object can be, for example, a hand, finger, or other body part of a user. The object can also be a special purpose device, such as a stylus or pen, or a special-purpose hardware device, such as a motion tracking stylus/remote which is communicatively coupled to the system and which contains accelerometers and/or tilt sensors. The object recognition can be performed by the virtual driver can be based upon earlier training, such as through a calibration routine run using the object.

FIG. 5A illustrates an example of object recognition according to an exemplary embodiment. As shown in FIG. 5A, image 501 includes a hand of the user that has been recognized as object 502. The recognition algorithm could of course be configured to recognize a different object, such as a finger.

Returning to FIG. 4, at step 403 one or more orientations and one or more positions of the recognized object are determined. This can be accomplished in a variety of ways. If the object is not a hardware device and is instead a body part, such as a hand or finger, the object can be mapped in a three-dimensional coordinate system using a known location of the camera as a reference point to determine the three dimensional coordinates of the object and the various angles relative to the X, Y, and Z axes. If the object is a hardware device and includes motion tracking hardware such as an accelerometer and/or tilt sensors, then the image information can be used in conjunction with the information indicated by the accelerometer and/or tilt sensors to determine the positions and orientations of the object.

At step 404 the user input is determined based at least in part on the one or more orientations and the one or more positions of the recognized object. This can include determining location coordinates on a transparent user interface (UI) of the transparent layer based at least in part the on the one or more orientations and the one or more positions. The transparent UI is part of the transparent layer and is superimposed on an underlying UI corresponding to the operating system and/or any applications executing on the operating system.

FIG. 5B illustrates an example of this step when the object is a user's finger. As shown in FIG. 5B, display device 503 includes an underlying UI 506 and a transparent UI 507 superimposed over the underlying UI 506. For the purpose of clarity, the transparent UI 507 is shown with dot shading, but it is understood that in practice the transparent UI is a transparent layer that is not visible to the user. Additionally, the transparent UI 507 is shown as slightly smaller than the underlying UI 506 but it is understood that in practice the transparent UI would cover the same screen area as the underlying UI.

As shown in FIG. 5B, the position and orientation information of the object (the user's finger) is used to project a line onto the plane of the display device 503 and determine an intersection point 505. The image information captured by camera 504 and the known position of the display device 503 under the camera can be used to aid in this projection. As shown in FIG. 5B, the user input is determined to be input coordinates at the intersection point 505.

As will be discussed further below, the actual transparent layer command that is generated based on this input can be based upon user settings and/or an identified context. For example, the command can be a touch command indicating that an object at the coordinates of point 505 should be selected and/or opened. The command can also be a pointing command indicating that a pointer (such as a mouse pointer) should be moved to the coordinates of point 505. Additionally, the command can be an edit command which modifies the graphical output at the location (such as to annotate the interface or draw an element).

While FIG. 5B shows the recognized object 502 as being at some distance from the display device 503, a touch input can be detected regardless of the distance. For example, if the user were to physically touch the display device 503, the technique described above would still determine the input coordinates. In that case, the projection line between object 502 and the intersection point would just be shorter.

Of course, touch inputs are not the only type of user input that can be determined from captured images. The step of determining a user input based at least in part on the one or more orientations and the one or more positions of the recognized object can include determining gesture input. In particular, the positions and orientations of a recognized object across multiple images could be analyzed to determine a corresponding gesture, such as a swipe gesture, a pinch gesture, and/or any known or customized gesture. The user can calibrate the virtual driver to recognize custom gestures that are mapped to specific contexts and commands within those contexts. For example, the user can create a custom gesture that is mapped to an operating system context and results in the execution of a native operating system command which launches a particular application.

As discussed earlier, the information captured by the one or more hardware devices in step 301 of FIG. 3 can also include sound information captured by a microphone. FIG. 6 illustrates a flowchart for determining a user input based at least in part on information captured by one or more hardware devices communicatively coupled to the system when the captured information is sound information. As discussed below, voice recognition is performed on the sound information to identify one or more words corresponding to the user input.

At step 601 the sound data is received. The sound data can be captured by a hardware device such as a microphone and received by the virtual driver, as discussed above. At step 602 the received sound data can be compared to a sound dictionary. The sound dictionary can include sound signatures of one or more recognized words, such as command words or command modifiers. At step 603 one or more words in the sound data are identified as the user input based on the comparison. The identified one or more words can then be converted into transparent layer commands and passed to the transparent layer.

As discussed earlier, the driver emulated by the virtual driver, the expected type of user input, and the command generated based upon the user input can all be determined based at least in part on one or more settings or prior user inputs.

FIG. 7 illustrates a tool interface 701 that can also be part of the transparent layer. Unlike the transparent UI, the tool interface 701 is visible to the user and can be used to select between different options which alter the emulation mode of the virtual driver, the native commands generated based on user input, or perform additional functions.

Button 701A allows a user to select the type of drawing tool used to graphically modify the user interface when the user input is input coordinates (such as coordinates based upon a user touching the screening with their hand or a stylus/remote). The various drawing tools can include different brushes, colors, pens, highlighters, etc. These tools can result in graphical alterations of varying styles, thicknesses, colors, etc.

Button 701B allows the user to switch between selection, pointing, or drawing modes when input coordinates are received as user input. In a selection mode, the input coordinates can be processed as a “touch” and result in selection or opening of an object at the input coordinates. In pointing mode the coordinates can be processed as a pointer (such as a mouse pointer) position, effectively allowing the user to emulate a mouse. In drawing mode, the coordinates can be processed as a location at which to alter the graphical output of the user interface to present the appearance of drawing or writing on the user interface. The nature of the alteration can depend on a selected drawing tool, as discussed with reference to button 701A. Button 701B can also alert the virtual driver to expect image input and/or motion input (if a motion tracking device is used) and to emulate the appropriate drivers accordingly.

Button 701C alerts the virtual driver to expect a voice command. This can cause the virtual driver to emulate drivers corresponding to a coupled microphone to receive voice input and to parse the voice input as described with respect to FIG. 6.

Button 701D opens a launcher application which can be part of the transparent layer and can be used to launch applications within the operating system or to launch specific commands within an application. Launcher can also be used to customize options in the transparent layer, such as custom voice commands, custom gestures, custom native commands for applications associated with user input and/or to calibrate hardware devices and user input (such as voice calibration, motion capture device calibration, and/or object recognition calibration).

Button 701E can be used to capture a screenshot of the user interface and to export the screenshot as an image. This can be used in conjunction with the drawing mode of button 701B and the drawing tools of 701A. After a user has marked up a particular user interface, the marked up version can be exported as an image.

Button 701F also allows for graphical editing and can be used to change the color of a drawing or aspects of a drawing that the user is creating on the user interface. Similar to the draw mode of button 701B, this button alters the nature of a graphical alteration at input coordinates.

Button 701G cancels a drawing on the user interface. Selection of this button can remove all graphical markings on the user interface and reset the underlying UI to the state it was in prior to the user creating a drawing.

Button 701H can be used to launch a whiteboard application that allows a user to create a drawing or write using draw mode on a virtual whiteboard.

Button 701I can be used to add textual notes to objects, such as objects shown in the operating system UI or an application UI. The textual notes can be interpreted from voice signals or typed by the user using a keyboard.

Button 701J can be used to open or close the tool interface 701. When closed, the tool interface can be minimized or removed entirely from the underlying user interface.

As discussed earlier, a stylus or remote hardware device can be used with the present system, in conjunction with other hardware devices, such as a camera or video camera. FIG. 8 illustrates an example of a stylus 801 that can be used with the system. The stylus 801 can communicate with a hardware receiver 802, such as over Bluetooth. The hardware receiver can connect to computer system, such as via USB 802B and the signals from the stylus passed to computer system via hardware receiver can be used to control and interact with menu 803, which is similar to the tool interface shown in FIG. 7.

As shown in FIG. 8, the stylus 801 can include physical buttons 801A. These physical buttons 801 can be used to power the stylus on, navigate the menu 803, and make selections. Additionally, the stylus 801 can include a distinctive tip 801B which is captured in images by a camera and recognized by the virtual driver. This can allow the stylus 801 to be used for drawing and editing when in draw mode. The stylus 801 can also include motion tracking hardware, such an accelerometer and/or tilt sensors to aid in position detection when the stylus is used to provide input coordinates or gestures. Additionally, the hardware receiver 802 can include a calibration button 802A, which when depressed, can launch a calibration utility in the user interface. This allows for calibration of the stylus.

Returning to FIG. 3, at step 302 a context is identified corresponding to the user input. The identified context comprises one of an operating system or an application executing on the operating system.

FIG. 9 illustrates a flowchart for identifying a context corresponding to the user input according to an exemplary embodiment. As shown in FIG. 9, operating system data 901, application data 902, and user input data 903 can all be used to determine a context 904.

Operating system data 901 can include, for example, information regarding an active window in the operating system. For example, if the active window is a calculator window, then the context can be determined to be a calculator application. Similarly, if the active window is a Microsoft Word window, then the context can be determined to be the Microsoft Word application. On the other hand, if the active window is a file folder, then the active context can be determined to be the operating system. Operating system data can also include additional information such as which applications are currently executing, a last launched application, and any other operating system information that can be used to determine context.

Application data 902 can include, for example, information about one or more applications that are executing and/or information mapping particular applications to certain types of user input. For example, a first application may be mapped to voice input so that whenever a voice command is received, the context is automatically determined to be the first application. In another example, a particular gesture can be associated with a second application, so that when that gesture is received as input, the second application is launched or closed or some action within the second application is performed.

User input 903 can also be used to determine the context in a variety of ways. As discussed above, certain types of user input can be mapped to certain applications. In the above example, voice input is associated with a context of a first application. Additionally, the attributes of the user input can also be used to determine a context. Gestures or motions can be mapped to applications or to the operating system. Specific words in voice commands can also be mapped to applications or to the operating system. Input coordinates can also be used to determine a context. For example, a window in the user interface at the position of the input coordinates can be determined and an application corresponding to that window can be determined as the context.

FIG. 10 illustrates an example of using the input coordinates to determine a context. As shown in FIG. 10, the display device 1001 is displaying a user interface 1002. Also shown is a camera 1004 and transparent layer 1003 superimposed over underlying user interface 1003. A user utilizes a stylus 1000 to point to location 1005 in user interface 1002. Since location 1005 lies within an application window corresponding to Application 1, then Application 1 can be determined to be the context for the user input, as opposed to Application 2, Application 3, or the Operating System.

Returning to FIG. 3, at step 303 the user input is converted into one or more transparent layer commands based at least in part on the identified context. As discussed earlier, the transparent layer comprises an application programming interface (API) configured to interface between the virtual driver and the operating system and/or an application executing on the operating system.

FIG. 11 illustrates a flowchart for converting user input into transparent layer commands. As shown at step 1104 of FIG. 11, the transparent layer command can be determined based at least in part on the identified context 1102 and the user input 1103. The transparent layer command can include one or more native commands configured to execute in one or more corresponding contexts. The transparent layer command can also include response outputs to be transmitted to the virtual driver and on to hardware device(s).

The identified context 1102 can be used to determine which transparent layer command should be mapped to the user input. For example, if the identified context is “operating system,” then a swipe gesture input can be mapped to a transparent layer command that results in the user interface scrolling through currently open windows within the operating system (by minimizing one open window and maximize a next open window). Alternatively, if the identified context is “web browser application,” then the same swipe gesture input can be mapped to a transparent layer command that results in a web page being scrolled.

The user input 1103 also determines the transparent layer command since user inputs are specifically mapped to certain native commands within one or more contexts and these native commands are part of the transparent layer command. For example, a voice command “Open email” can be mapped to a specific operating system native command to launch the email application Outlook. When voice input is received that includes the recognized words “Open email,” this results in a transparent layer command being determined which includes the native command to launch Outlook.

As shown in FIG. 11, transparent layer commands can also be determined based upon one or more user settings 1101 and API libraries 1104. API libraries 1104 can be used to lookup native commands corresponding to an identified context and particular user input. In the example of the swipe gesture and a web browser application context, the API library corresponding to the web browser application can be queried for the appropriate API calls to cause scrolling of a web page. Alternatively, the API libraries 1104 can be omitted and native commands can be mapped directed to a particular user inputs and identified contexts.

In the situation where the user input is determined to be input coordinates the transparent layer command is determined based at least in part on the input location coordinates and the identified context. In this case, the transparent layer command can include at least one native command in the identified context, the at least one native command being configured to perform an action at the corresponding location coordinates in the underlying UI.

When there is more than one possible action mapped to a particular context and user input, settings 1101 can be used to determine the corresponding transparent layer command. For example, button 701B of FIG. 7 allows user to select between selection, pointing, or draw modes when input coordinates are received as user input. This setting can be used to determine the transparent layer command, and by extension, which native command is performed and which action is performed. In this case, the possible native commands can include a selection command configured to select an object associated with the corresponding location coordinates in the underlying UI, a pointer command configured to move a pointer to the corresponding location coordinates in the underlying UI, and a graphical command configured to alter the display output at the corresponding location coordinates in the underlying UI.

FIG. 12A illustrates an example of receiving input coordinates when the selection mode is toggled. As shown in FIG. 12A, the user has pointed stylus 1200 at operating system UI 1202 (having superimposed transparent UI 1203) on display device 1201. Similar to earlier examples, camera 1204 can be used to determine the position and orientation information for stylus 1200 and the input coordinates. Since the selection mode is toggled and the stylus 1200 is pointed at folder 1205 within the operating system UI 1202, the determined transparent layer command can include a native operating system command to select an object associated with the input coordinates (which in this case is folder 1205). In another example, if a window was located at the input coordinates, this would result in selection of the entire window.

FIG. 12B illustrates an example of receiving input coordinates when the pointing mode is toggled. In this case, the determined transparent layer command can include a native operating system command to move mouse pointer 1206 to the location of the input coordinates.

FIG. 12C illustrates an example of receiving input coordinates when the drawing mode is toggled and the user has swept stylus 1200 over multiple input coordinates. In this case, the determined transparent layer command can include a native operating system command to alter the display output at the locations of each of the input coordinates, resulting in the user drawing line 1207 on the user interface 1202. The modified graphical output produced in drawing mode can be stored as part of the transparent layer 1203, for example, as metadata related to a path of input coordinates. The user can then select an option to export the altered display output as an image.

In the situation wherein the user input is identified as a gesture, converting the user input into one or more transparent layer commands based at least in part on the identified context can include determining a transparent layer command based at least in part on the identified gesture and the identified context. The transparent layer command can include at least one native command in the identified context, the at least one native command being configured to perform an action associated with the identified gesture in the identified context. An example of this is discussed above with respect to a swipe gesture and a web browser application context that results in a native command configured to perform a scrolling action in the web browser.

In the situation wherein the user input is identified as one or more words (such as by using voice recognition), converting the user input into one or more transparent layer commands based at least in part on the identified can include determining a transparent layer command based at least in part on the identified one or more words and the identified context. The transparent layer command can include at least one native command in the identified context, the at least one native command being configured to perform an action associated with the identified one or more words in the identified context.

FIG. 13 illustrates an example of a transparent layer command 1300 determined based on one or more words identified in input voice data. The identified words 1301 include one of the phrases “whiteboard” or “blank page.” Transparent layer command 1300 also includes a description 1302 of the command, and response instructions 1303 which are output instructions sent by the transparent layer to the virtual driver and to a hardware output device upon execution of the transparent layer command. Additionally, transparent layer command 1300 includes the actual native command 1304 used to call the white board function.

FIG. 14 illustrates another example of a transparent layer command 1400 determined based on one or more words identified in input voice data according to an exemplary embodiment. In this example, the one or more words are “open email.” As shown in FIG. 14, the transparent layer command 1400 includes the native command “outlook.exe,” which is an instruction to run a specific executable file that launches the outlook application. Transparent layer command 1400 also includes a voice response “email opened” which will be output in response to receiving the voice command.

Returning to FIG. 3, at step 304 the one or more transparent layer commands are executed on the transparent layer. Execution of the one or more transparent layer commands is configured to cause execution of one or more native commands in the identified context.

FIG. 15 illustrates a flowchart for executing the one or more transparent layer commands on the transparent layer according to an exemplary embodiment. At step 1501 at least one native command in the transparent layer command is identified. The native command can be, for example, designated as a native command within the structure of the transparent layer command, allowing for identification.

At step 1502 the at least one native command is executed in the identified context. This step can include passing the at least one native command to the identified context via an API identified for that context and executing the native command within the identified context. For example, if the identified context is the operating system, then the native command can be passed to the operating system for execution via the operating system API. Additionally, if the identified context is an application, then the native command can be passed to application for execution via the application API.

Optionally, at step 1503, a response can be transmitted to hardware device(s). As discussed earlier, this response can be routed from the transparent layer to the virtual driver and on to the hardware device.

FIGS. 16-19 illustrate additional features of the system disclosed herein. FIG. 16 illustrates an example interface for adding new commands corresponding to user input according to an exemplary embodiment. The dashboard in interface 1600 includes icons of applications 1601 which have already been added and can be launched using predetermined user inputs and hardware devices (e.g., voice commands). The dashboard can also show other commands that are application-specific and that are mapped to certain user inputs. Selection of addition button 1602 opens the add command menu 1603. This menu allows users to select between the following options: Item type: Fixed Item to add on bottom bar menu/Normal Item to add in a drag menu; Icon: Select the image icon; Background: Select the background icon color; Color: Select the icon color; Name: Set the new item name; Voice command: Set the voice activation command to open the new application; Feedback response: Set the application voice response feedback; Command: Select application type or custom command type to launch (e.g., launch application command, perform action within application command, close application command, etc.); Process Start: if launching a new process or application, the name of the process or application; and Parameter: any parameters to pass into the new process or application.

FIG. 17 illustrates various components and options of the drawing interface 1700 and draw mode according to an exemplary embodiment. FIG. 18 illustrates a calibration and settings interface 1800 for a video camera hardware device that is used to recognize objects and allows for a user to provide input using touch and gestures. FIG. 19 illustrates a general settings interface 1900 which allows a user to customize various aspects of the interface, toggle input modes, and make other changes. As shown in interface 1900, a user can also access a settings page to calibrate and adjust settings for a hardware stylus (referred to as the “Magic Stylus”).

The system disclosed herein can be implemented on multiple networked computing devices and used an aid in conducting networked collaboration sessions. For example, the whiteboard functionality described earlier can be a shared whiteboard between multiple users on multiple computing devices.

However, one of the problems with existing whiteboards or other shared collaborations spaces is that there is no easy way to share files with connected participants. While certain applications allow the entire group to review files, such as documents, over the collaboration space, in order for a user to share a file with another user, it is necessary to open a new application (such as an email client or file sharing application) in order to transmit the file to the other user. During shared collaboration sessions, this frequently interrupts the workflow and shared brainstorming sessions that the collaboration space was designed to promote.

In addition to the earlier described methods and systems for implementation of a universal hardware-software interface, Applicant has additionally discovered methods, apparatuses and computer-readable media that allow for real-time transmission of files over a web socket connection during a collaboration session between networked computers.

FIG. 20 illustrates a flowchart for transmission of files over a web socket connection in a networked collaboration workspace according to an exemplary embodiment. All of the steps shown in FIG. 20 can be performed on a local computing device, such as a client device connected to a server, and do not require multiple computing devices.

At step 2001 a representation of a collaboration workspace hosted on a server and accessible to a plurality of participants over a web socket connection is transmitted on a user interface of a local computing device. The representation of the collaboration workspace can include one or more remote participant objects corresponding to one or more remote computing devices connected to the server. As used herein, remote computing devices and remote participants refers to computing devices and participants other than the local participant and the local computing device. Remote computing devices are separated from the local device by a network, such as a wide area network (WAN).

FIG. 21A illustrates the network architecture used to host and transmit collaboration workspace according to an exemplary embodiment. As shown in FIG. 21A, server 2100 is connected to computing devices 2101A-2101F. The server 2100 and computing devices 2101A-2101F can be connected via a network connection, such as web socket connection, that allows for bi-directional communication between the computing devices 2101A-2101F (clients) and the server 2100. As shown in FIG. 21A, the computing devices can be any type of computing device, such as a laptop, desktop, smartphone, or other mobile device.

The collaboration workspace can be, for example, a digital whiteboard configured to propagate any edits from any participants in the plurality of participants to other participants over the web socket connection. FIG. 21B illustrates the process for propagating edits to the collaboration workspace within the network according to an exemplary embodiment. As shown in FIG. 21B, if a user at computing device 2101B makes an edit or an alteration to the collaboration workspace, this edit or alteration 2102B is sent to the server 2100, where it is used to update the hosted version of the workspace. The edit or alteration is then propagated as updates 2102A, 2102C, 2102D, 2102E, and 2102F by the server 2100 to the other connected computing devices 2101A, 2101C, 2101D, 2101E, and 2101F.

Each representation of the collaboration workspace can be a version of the collaboration workspace that is customized to a local participant. For example, as discussed above, each representation of the collaboration workspace can include one or more remote participant objects corresponding to one or more remote computing devices connected to the server.

FIG. 22 illustrates multiple representations of a collaboration workspace according to an exemplary embodiment. As shown in FIG. 22, server 2200 hosts collaboration workspace 2201. The version of the collaboration workspace hosted on the server is propagated to the connected devices, as discussed earlier. FIG. 22 also illustrates the representations of the collaboration workspace for three connected users, User 1, User 2, and User 3. As shown, each representation is customized to the local participant (to the local computing device). For example, representation 2201A for User 1 includes remote participant objects corresponding to User 2 and User 3. Similarly, representation 2201B for User 2 includes remote participant objects corresponding to User 1 and User 3 and representation 2201C for User 3 includes remote participant objects corresponding to User 1 and User 2.

The remote participant objects indicate a remote participant and can take many forms. For example, a remote participant object can be an embedded video stream of a remote participant that is connected via videoconference or webcam. The remote participant object can also be an icon representing the remote participant, an avatar of the remote participant, or any other visual or audio indicator of a particular remote participant. The remote participant objects can be custom objects that can be dragged, moved and/or resized within the representation of the workspace.

Returning to FIG. 20, at step 2002 one or more live folders corresponding to the one or more remote participant objects are generated on the local computing device, with each live folder being mapped to a network address of a remote computing device corresponding to the remote participant object.

FIG. 23 illustrates a flowchart for generating one or more live folders corresponding to the one or more remote participant objects according to an exemplary embodiment.

At step 201, the local computing device queries the server for one or more Internet Protocol (IP) addresses of one or more remote computing devices corresponding to the one or more remote participant objects.

FIG. 24 illustrates an example of this querying process. As shown in FIG. 24, computing devices 2401A, 2402, and 2403 are all connected to server 2400 over a bi-directional network connection, such as a web socket connection. Server hosts a collaboration workspace (not shown). FIG. 24 also shows the representation 2401B of the collaboration workspace that is visible on a user interface of computing device 2401A. Representation 2401B includes remote participant objects corresponding to User 2 and User 3, who are the users of computing devices 2402 and 2403, respectively. As shown in FIG. 24, a query for the IP addresses (or other type of network addresses) of remote computing devices corresponding to the remote participant objects is transmitted over the network connection from computing device 2401A to server 2400. In response, server transmits the IP addresses (or other type of network addresses) of the other connected computing devices 2402 and 2403 to computing device 2401A (the requesting computing device). Server can also transmit information that allows computing device 2401A to identify which IP address corresponds to which remote participant object, such as a user identification or other information.

Returning to FIG. 23, at step 2302 the local computing device generates one or more local folders corresponding to the one or more remote participant objects. The one or more local folders can be generated and stored on a memory of the local computing device. For example, a temporary cache can be created on the local computing device when the collaboration workspace session is initiated. This temporary cache store information about the session, such as the meeting identifier and other session details. The one or more local folders can be generated and stored within the temporary cache.

FIG. 25 illustrates an example of generating one or more local folders corresponding to the one or more remote participants according to an exemplary embodiment. The local computing device 2500 includes a display (not shown) that displays the user interface 2501, including a representation 2502 of the collaboration workspace. Collaboration workspace representation 2502 includes two remote participant objects, corresponding to User 2 and User 3. As shown in FIG. 25, local folders F2 and F3 are created within local storage 2503 on the computing device 2500 and linked with the remote participant objects for User 2 and User 3. The folders can be linked to the remote participant objects in a variety of ways. For example, a custom data structure can be created that associates each remote participant object with a local folder. The local folder can be incorporated as an invisible element into the user interface 2501 and placed at the same position of the corresponding remote participant object. The remote participant object can have an exposed API that allows for linking to a corresponding local folder. Many variations are possible and these examples are not intended to be limiting.

Returning to FIG. 23, at step 2303 one or more live folders are generated by mapping the one or more local folders to the one or more IP addresses.

FIG. 26 illustrates an example of mapping the one or more local folders to the one or more IP addresses according to an exemplary embodiment. The local computing device 2600 includes a display (not shown) that displays the user interface 2601, including the collaboration workspace 2602. Collaboration workspace representation 2602 includes two remote participant objects, corresponding to User 2 and User 3. Local folders F2 and F3 within local storage 2603 on the computing device 2600 are linked with the remote participant objects for User 2 and User 3 in collaboration workspace representation 2602.

As shown in FIG. 26, local folders F2 and F3 are mapped to the network addresses of remote computing devices 2604 and 2605, respectively. Computing device 2604 corresponds to remote participant User 2 and computing device 2605 corresponds to remote participant User 3. The mapping of the local folders to the network addresses of the remote computing devices can be accomplished in a variety of ways. Each local folder can have, as its address, the network address of the corresponding remote computing device. In this case, the local folder is an instantiation of remote folder on the local storage. Additionally, a custom data structure or script can be configured to transfer the contents of a local folder to a destination network address. The script can interface with the network connection (such as the web socket) in order to effectuate the transfer. Many variations are possible and these examples are not intended to be limiting.

Returning to FIG. 20, at step 2003 a user input to drag at least one icon corresponding to at least one file proximate to a remote participant object in the one or more remote participant objects is detected by the local computing device, with the remote participant object corresponding to a remote computing device in the one or more remote computing devices. This is commonly referred to as a drag-and-drop action and can be input using a variety of input devices. For example, a user can drag-and-drop using a mouse. A user can also drag-and-drop using a hand gesture or stylus as discussed earlier. The earlier described techniques involving the virtual driver and/or the transparent can be used to detect the drag and drop motion.

The local computing device can be configured to store one or more spatial positions of one or more remote participant objects within the user interface. The detection of whether a particular icon has been dragged and dropped proximate to a particular remote participant object can be performed by detecting a user input to drag an icon to a destination spatial position that is within a threshold distance from a spatial position of the remote participant object. The threshold distance can be set by a user or can be some default value. For example, the threshold distance can be less than 10 pixels or less than zero pixels (in which case the dragged icon would have to intersect or overlap with the remote participant object in the user interface).

FIG. 27 illustrates an example of the drag and drop process and detection according to an exemplary embodiment. User interface 2701 include a representation 2702 of a collaboration workspace, including remote participant objects corresponding to User 2 (U2) and User 3 (U3). Interface 2701 also includes a file window or file interface 2703, which can be, for example, an open folder in a file browser. File interface 2703 can also be a desktop of the local computing device, a file sharing application, a web browser, or any other application. As shown in FIG. 27, a user has dragged a file “D3” to the remote participant object for User 3 (U3).

Of course, the file can also be dragged from within the collaboration workspace. FIG. 28 illustrates another example of the drag and drop process and detection according to an exemplary embodiment. Interface 2801 corresponds to a representation of the collaboration workspace. Interface portion 2802 can be a section of the representation of the collaboration workspace listing various files. Additionally, in this case, the remote participant object 2803 is an embedded video stream, which can be received over the network (e.g., web socket) connection. As shown in FIG. 28, a local participant (user) has dragged an adobe file 2804 to the remote participant object 2803. Of course, the file can be any type of file, such as an audio file, video file, audiovisual file, a text document, a spreadsheet, a slide presentation, etc.

Returning to FIG. 20, at step 2004 the at least one file is stored in a live folder corresponding to the remote participant object by the local computing device to thereby transmit the at least one file to the network address of the remote computing device over the web socket connection (or other network connection).

FIG. 29 illustrates a flowchart for storing the at least one file in a live folder corresponding to the remote participant object and to transmit the at least one file to the network address of the remote computing device over the web socket connection according to an exemplary embodiment.

At step 2901 the at least one file corresponding to the at least one dragged icon is stored in the live folder. At step 2902 a copy of the at least one file is transmitted to the mapped network address through the web socket connection (or other network connection). The web socket connection can be configured to route data stored in the live folder to the mapped network address via the server. This routing can be performed similar to the update shown in FIG. 21B, except that the file is transmitted to a specific remote computing device and not propagated to all connected remote computing devices. For example, the file can be transmitted over the web socket to the server, where the destination address can be used by the server to further route the file over the web socket to the appropriate destination remote computing device.

Since a web socket connection is already established as part of the collaboration workspace and/or as part of a video conference (when the remote participant object is an embedded video stream), the described process utilizes the web socket to perform routing of files to the intended recipient.

At step 2903 the at least one file can be deleted from the live folder upon completion of the transmission. For example, if the live folder is stored in a temporary cache on the local computing device, once a copy a file stored in the live folder has been transmitted (such as by streaming) to the remote computing device, the file stored in the local live folder can be deleted.

One or more of the above-described techniques can be implemented in or involve one or more computer systems. FIG. 30 illustrates an example of a specialized computing environment 3000. The computing environment 3000 is not intended to suggest any limitation as to scope of use or functionality of a described embodiment(s).

With reference to FIG. 30, the computing environment 3000 includes at least one processing unit 3010 and memory 3020. The processing unit 3010 executes computer-executable instructions and can be a real or a virtual processor. In a multi-processing system, multiple processing units execute computer-executable instructions to increase processing power. The memory 3020 can be volatile memory (e.g., registers, cache, RAM), non-volatile memory (e.g., ROM, EEPROM, flash memory, etc.), or some combination of the two. The memory 3020 can store software 3080 implementing described techniques.

A computing environment can have additional features. For example, the computing environment 3000 includes storage 3040, one or more input devices 3050, one or more output devices 3060, and one or more communication connections 3090. An interconnection mechanism 3070, such as a bus, controller, or network interconnects the components of the computing environment 3000. Typically, operating system software or firmware (not shown) provides an operating environment for other software executing in the computing environment 3000, and coordinates activities of the components of the computing environment 3000.

The storage 3040 can be removable or non-removable, and includes magnetic disks, magnetic tapes or cassettes, CD-ROMs, CD-RWs, DVDs, or any other medium which can be used to store information and which can be accessed within the computing environment 3000. The storage 3040 can store instructions for the software 3080.

The input device(s) 3050 can be a touch input device such as a keyboard, mouse, pen, trackball, touch screen, or game controller, a voice input device, a scanning device, a digital camera, remote control, or another device that provides input to the computing environment 3000. The output device(s) 3060 can be a display, television, monitor, printer, speaker, or another device that provides output from the computing environment 3000.

The communication connection(s) 3090 enable communication over a communication medium to another computing entity. The communication medium conveys information such as computer-executable instructions, audio or video information, or other data in a modulated data signal. A modulated data signal is a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media include wired or wireless techniques implemented with an electrical, optical, RF, infrared, acoustic, or other carrier.

Implementations can be described in the context of computer-readable media. Computer-readable media are any available media that can be accessed within a computing environment. By way of example, and not limitation, within the computing environment 3000, computer-readable media include memory 3020, storage 3040, communication media, and combinations of any of the above.

Of course, FIG. 30 illustrates computing environment 3000, display device 3060, and input device 3050 as separate devices for ease of identification only. Computing environment 3000, display device 3060, and input device 3050 can be separate devices (e.g., a personal computer connected by wires to a monitor and mouse), can be integrated in a single device (e.g., a mobile device with a touch-display, such as a smartphone or a tablet), or any combination of devices (e.g., a computing device operatively coupled to a touch-screen display device, a plurality of computing devices attached to a single display device and input device, etc.). Computing environment 3000 can be a set-top box, personal computer, or one or more servers, for example a farm of networked servers, a clustered server environment, or a cloud network of computing devices.

Having described and illustrated the principles of our invention with reference to the described embodiment, it will be recognized that the described embodiment can be modified in arrangement and detail without departing from such principles. Elements of the described embodiment shown in software can be implemented in hardware and vice versa.

In view of the many possible embodiments to which the principles of our invention can be applied, we claim as our invention all such embodiments as can come within the scope and spirit of the following claims and equivalents thereto. 

We claim:
 1. A method for transmission of files over a web socket connection in a networked collaboration workspace, the method comprising: transmitting, on a user interface of a local computing device, a representation of a collaboration workspace hosted on a server and accessible to a plurality of participants over a web socket connection, the representation of the collaboration workspace comprising one or more remote participant objects corresponding to one or more remote computing devices connected to the server; generating, on the local computing device, one or more live folders corresponding to the one or more remote participant objects, each live folder being mapped to a network address of a remote computing device corresponding to the remote participant object; detecting, by the local computing device, a user input to drag at least one icon corresponding to at least one file proximate to a remote participant object in the one or more remote participant objects, the remote participant object corresponding to a remote computing device in the one or more remote computing devices; and storing, by the local computing device, the at least one file in a live folder corresponding to the remote participant object to thereby transmit the at least one file to the network address of the remote computing device over the web socket connection.
 2. The method of claim 1, wherein the one or more remote participant objects corresponding to the one or more remote computing devices comprise one or more of: an embedded video stream or a remote participant icon.
 3. The method of claim 1, wherein the collaboration workspace comprises a digital whiteboard configured to propagate any edits from any participants in the plurality of participants to other participants over the web socket connection and wherein the representation of collaboration workspace comprises a representation of the digital whiteboard customized to a local participant.
 4. The method of claim 1, wherein generating one or more live folders corresponding to the one or more remote participant objects comprises: querying the server for one or more Internet Protocol (IP) addresses of the one or more remote computing devices corresponding to the one or more remote participant objects; generating one or more local folders corresponding to the one or more remote participant objects; and generating the one or more live folders by mapping the one or more local folders to the one or more IP addresses.
 5. The method of claim 1, wherein the local computing device is configured to store one or more spatial positions of the one or more remote participant objects within the user interface and wherein detecting a user input to drag at least one icon corresponding to at least one file proximate to a remote participant object in the one or more remote participant objects comprises: detecting a user input to drag the at least one icon to a destination spatial position that is within a threshold distance from a spatial position of the remote participant object.
 6. The method of claim 1, wherein storing the at least one file in a live folder corresponding to the remote participant object to thereby transmit the at least one file to the network address of the remote computing device over the web socket connection comprises: storing the at least one file in the live folder; transmitting a copy of the at least one file to the mapped network address through the web socket connection, wherein the web socket connection is configured to route data to the mapped network address via the server; and deleting the at least one file from the live folder upon completion of the transmission.
 7. The method of claim 1, wherein the live folder is stored in a temporary cache on the local computing device.
 8. A local computing device for transmission of files over a web socket connection in a networked collaboration workspace, the local computing device comprising: one or more processors; and one or more memories operatively coupled to at least one of the one or more processors and having instructions stored thereon that, when executed by at least one of the one or more processors, cause at least one of the one or more processors to: transmit, on a user interface of the local computing device, a representation of a collaboration workspace hosted on a server and accessible to a plurality of participants over a web socket connection, the representation of the collaboration workspace comprising one or more remote participant objects corresponding to one or more remote computing devices connected to the server; generate one or more live folders corresponding to the one or more remote participant objects, each live folder being mapped to a network address of a remote computing device corresponding to the remote participant object; detect a user input to drag at least one icon corresponding to at least one file proximate to a remote participant object in the one or more remote participant objects, the remote participant object corresponding to a remote computing device in the one or more remote computing devices; and store the at least one file in a live folder corresponding to the remote participant object to thereby transmit the at least one file to the network address of the remote computing device over the web socket connection.
 9. The local computing device of claim 8, wherein the one or more remote participant objects corresponding to the one or more remote computing devices comprise one or more of: an embedded video stream or a remote participant icon.
 10. The local computing device of claim 8, wherein the collaboration workspace comprises a digital whiteboard configured to propagate any edits from any participants in the plurality of participants to other participants over the web socket connection and wherein the representation of collaboration workspace comprises a representation of the digital whiteboard customized to a local participant.
 11. The local computing device of claim 8, wherein the instructions that, when executed by at least one of the one or more processors, cause at least one of the one or more processors to generate one or more live folders corresponding to the one or more remote participant objects further cause at least one of the one or more processors to: query the server for one or more Internet Protocol (IP) addresses of the one or more remote computing devices corresponding to the one or more remote participant objects; generate one or more local folders corresponding to the one or more remote participant objects; and generate the one or more live folders by mapping the one or more local folders to the one or more IP addresses.
 12. The local computing device of claim 8, wherein the local computing device is configured to store one or more spatial positions of the one or more remote participant objects within the user interface and wherein the instructions that, when executed by at least one of the one or more processors, cause at least one of the one or more processors to detect a user input to drag at least one icon corresponding to at least one file proximate to a remote participant object in the one or more remote participant objects further cause at least one of the one or more processors to: detect a user input to drag the at least one icon to a destination spatial position that is within a threshold distance from a spatial position of the remote participant object.
 13. The local computing device of claim 8, wherein the instructions that, when executed by at least one of the one or more processors, cause at least one of the one or more processors to store the at least one file in a live folder corresponding to the remote participant object to thereby transmit the at least one file to the network address of the remote computing device over the web socket connection further cause at least one of the one or more processors to: store the at least one file in the live folder; transmit a copy of the at least one file to the mapped network address through the web socket connection, wherein the web socket connection is configured to route data to the mapped network address via the server; and delete the at least one file from the live folder upon completion of the transmission.
 14. The local computing device of claim 8, wherein the live folder is stored in a temporary cache on the local computing device.
 15. At least one non-transitory computer-readable medium storing computer-readable instructions that, when executed by a local computing device, cause the local computing device to: transmit, on a user interface of the local computing device, a representation of a collaboration workspace hosted on a server and accessible to a plurality of participants over a web socket connection, the representation of the collaboration workspace comprising one or more remote participant objects corresponding to one or more remote computing devices connected to the server; generate one or more live folders corresponding to the one or more remote participant objects, each live folder being mapped to a network address of a remote computing device corresponding to the remote participant object; detect a user input to drag at least one icon corresponding to at least one file proximate to a remote participant object in the one or more remote participant objects, the remote participant object corresponding to a remote computing device in the one or more remote computing devices; and store the at least one file in a live folder corresponding to the remote participant object to thereby transmit the at least one file to the network address of the remote computing device over the web socket connection.
 16. The at least one non-transitory computer-readable medium of claim 15, wherein the one or more remote participant objects corresponding to the one or more remote computing devices comprise one or more of: an embedded video stream or a remote participant icon.
 17. The at least one non-transitory computer-readable medium of claim 15, wherein the collaboration workspace comprises a digital whiteboard configured to propagate any edits from any participants in the plurality of participants to other participants over the web socket connection and wherein the representation of collaboration workspace comprises a representation of the digital whiteboard customized to a local participant.
 18. The at least one non-transitory computer-readable medium of claim 15, wherein the instructions that, when executed by the local computing device, cause the local computing device to generate one or more live folders corresponding to the one or more remote participant objects further cause the local computing device to: query the server for one or more Internet Protocol (IP) addresses of the one or more remote computing devices corresponding to the one or more remote participant objects; generate one or more local folders corresponding to the one or more remote participant objects; and generate the one or more live folders by mapping the one or more local folders to the one or more IP addresses.
 19. The at least one non-transitory computer-readable medium of claim 15, wherein the local computing device is configured to store one or more spatial positions of the one or more remote participant objects within the user interface and wherein the instructions that, when executed by the local computing device, cause the local computing device to detect a user input to drag at least one icon corresponding to at least one file proximate to a remote participant object in the one or more remote participant objects further cause the local computing device to: detect a user input to drag the at least one icon to a destination spatial position that is within a threshold distance from a spatial position of the remote participant object.
 20. The at least one non-transitory computer-readable medium of claim 15, wherein the instructions that, when executed by the local computing device, cause the local computing device to store the at least one file in a live folder corresponding to the remote participant object to thereby transmit the at least one file to the network address of the remote computing device over the web socket connection further cause the local computing device to: store the at least one file in the live folder; transmit a copy of the at least one file to the mapped network address through the web socket connection, wherein the web socket connection is configured to route data to the mapped network address via the server; and delete the at least one file from the live folder upon completion of the transmission. 